Systems and methods for image capture signature data storage

ABSTRACT

A transaction card construction and computer-implemented methods for a transaction card are described. The transaction card has vector formatted visible information lasered onto its surface. In some embodiments, systems and methods are disclosed for enabling the sourcing of visible information using a scalable vector format. The systems and methods may receive a request to add a first plurality of visible information to a transaction card and capture an image of the first plurality of visible information. The systems and methods may also map the image to a bounding box and convert the mapped image into vector format. In addition, the systems and methods may provide the converted image to a laser machine.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/000,451, filed on Aug. 24, 2020, which is a continuation of U.S.patent application Ser. No. 16/212,886, filed on Dec. 7, 2018, whichissued as U.S. Pat. No. 10,789,599 on Sep. 29, 2020, which is acontinuation of U.S. patent application Ser. No. 15/702,213, filed onSep. 12, 2017, which issued as U.S. Pat. No. 10,192,221 on Jan. 29,2019, which claims priority under 35 U.S.C. § 119 to U.S. ProvisionalApplication No. 62/470,053, filed on Mar. 10, 2017. The disclosures ofthe above-referenced applications are expressly incorporated herein byreference in their entireties.

DESCRIPTION Technical Field

The disclosed embodiments generally relate to the capturing of imagesand lasering of images on transaction cards using a vector image format.The disclosed embodiments also generally relate to electronicallyverifying visible information entered into a point-of-service terminalwith a scalable vector image file representing the visible informationstored for a transaction card.

Background

Transaction cards, such as credit and debit cards, have become a primarymeans for individuals to complete transactions involving data exchange.Traditional transaction cards are constructed in a sheeted laminatepress. The shape of the card is die cut, and then, the card ispersonalized. Typically, transaction cards are cut from laminated sheetsof polyvinyl chloride (PVC), polycarbonate (PC), or other similarmaterials. After the overall shape of the card is formed, the card maybe modified to add functional and/or visible features. For example, amagnetic stripe and/or microchip may be affixed to one side, the cardmay be stamped with the card number and customer name, and color(s) or adesign may be added for appearance.

As a fraud prevention measure, such cards may be provided with asignature specimen, such that a vendor relying on the card for someaspect of a transaction, can authenticate that the person presenting thecard is the actual authorized user of the card based on a comparison ofa fresh signature provided at presentation with a signature specimenavailable on the card. Traditional signature specimens are placed on thecard by the card user when the card user initially receives the card.Such timing, however, can allow an illicit recipient to place afraudulent signature specimen on the card, for fraudulent presentmentlater. Receiving a signature specimen from a card user prior to issuanceof the card, and forming an image of the signature on the card prior todelivery to the card user, precludes an illicit recipient from beingable to create a fraudulent signature specimen.

Traditional card manufacturing methods continue to utilize techniquesand materials that restrict variations in card style and appearance. Onelimitation of traditional transaction cards involves the quality of bothprinted and stored visible information, such as the customer'ssignature, name, or the like. Current techniques, for example, where asignature specimen is placed on a card by the card fabricator, utilizedigitized image formats (referred to as bitmaps), raster files, or flatimage files, such as in Portable Network Graphics (PNG) and JointPhotographic Experts Group (JPEG) formats, where the image is formed bya matrix of black or white dots (or colored dots in a color image), witheach dot at a specific position within the array being black, white, ora color, dependent on the image. Such arrays allow for imagerepresentation at high resolutions, to avoid “blockiness” being visible.However, higher resolutions increase data and processing requirements,and may be beyond the capabilities of image fixing processes, such asmatrix printing or forming processes. Furthermore, some forming methodsdo not utilize a matrixed-image-generation process, but rather acontinuous-element process, which utilizes continuous motion of agenerating tool, such as an etching laser, where the use of a bitmap orflat image would require conversion to vectored motion instructions forthe image generating tool. Thus, these flat image formats do notmaximize the ability of a laser machine to etch higher resolutionimages. When flat image formats are used, laser machines approximate theboundaries of an image, which often leads to etching lower qualityimages due to problems, such as aliasing problems. This approximationleads to lower quality images with more blur, less smooth motions, morepixelation, less sharpness, less fidelity, etc. Furthermore, lower imagequality of a signature specimen can also decrease fraud prevention andsecurity protections due to the signature specimen having a lowercomparability to an actual signature.

In addition, as transaction cards increase in prevalence, consumerexpectations for transaction card quality have increased. Transactioncards have increasingly been made to meet higher standards regardingmaterials, durability, security, and appearance. Decreased image qualitynegatively impacts the ability for transaction card manufacturers tomeet these higher standards.

The present disclosure is directed to improvements in transaction cards.Specifically, the present disclosure is directed to increasing thefidelity of visible information on transaction cards by employing avector format lasering engine.

SUMMARY

In the following description certain aspects and embodiments of thepresent disclosure will become evident. It should be understood that thedisclosure, in its broadest sense, could be practiced without having oneor more features of these aspects and embodiments. It should also beunderstood that these aspects and embodiments are merely exemplary.

The disclosed embodiments generally relate to a process/method andsystem for the capturing of images and lasering of the captured imageson transaction cards using a vector image format. The disclosedembodiments also generally relate to electronically verifying visibleinformation entered into a point-of-service terminal with a scalablevector image file representing the visible information stored for atransaction card.

Certain disclosed embodiments provide systems and computer-implementedmethods for the sourcing of visible information using a scalable vectorformat. For example, the method may include the step of receiving arequest to add a first plurality of visible information. The method mayalso include the step of capturing an image of the first plurality ofvisible information. The method may further include the step of mappingthe image of the first plurality of visible information to a boundingbox. The method may also include the step of converting the image into avector format. Even further, the method may include the step ofproviding the converted image to a laser machine, wherein providing theconverted image causes the laser machine to modify a card to include theconverted image.

Certain other disclosed embodiments provide systems andcomputer-implemented methods for electronically verifying information ona transaction card. For example, the method may include the step ofreceiving a request to provide a verification status for the transactioncard. The method may also include the step of receiving first visibleinformation, the first visible information comprising a signature of acustomer written on a point-of-sale terminal. The method may furtherinclude the step of receiving second visible information, the secondvisible information comprising a vector representation of a usersignature on a transaction card. The method may also include the step ofdetermining the verification status based on a comparison of the firstvisible information to the second visible information, which maycomprises the steps of running a similarity analysis between the firstand second visible information, calculating a score based on thesimilarity analysis, and comparing the score with a first predeterminedthreshold. Even further, the method may also include the step of sendingthe verification status.

In accordance with additional embodiments of the present disclosure, acomputer-readable medium is disclosed that stores instructions that,when executed by a processor(s), causes the processor(s) to performoperations consistent with one or more disclosed methods.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory only,and are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate disclosed embodiments and,together with the description, serve to explain the disclosedembodiments. In the drawings:

FIG. 1A is a front view of an exemplary transaction card, consistentwith disclosed embodiments;

FIG. 1B is a rear view of the exemplary transaction card of FIG. 1A,consistent with disclosed embodiments;

FIG. 1C is an edge view of the exemplary transaction card of FIG. 1A,consistent with disclosed embodiments;

FIG. 2 is a schematic diagram illustrating an exemplary systemenvironment to enable the sourcing of visible information using ascalable vector format, consistent with disclosed embodiments;

FIG. 3 is a block diagram of an exemplary visible information engine toperform functions of the disclosed methods, consistent with disclosedembodiments;

FIG. 4 is a flowchart of an exemplary process for electronicallyenabling the sourcing of visible information using a scalable vectorformat, consistent with disclosed embodiments;

FIG. 5 is a schematic diagram illustrating an exemplary transactionsystem, consistent with disclosed embodiments;

FIG. 6 is a flowchart of an exemplary process for electronicallyverifying visible information entered into a point-of-service terminalwith a scalable vector formatted file representing the visibleinformation stored for a transaction card, consistent with disclosedembodiments.

DETAILED DESCRIPTION

Reference will now be made in detail to the disclosed embodiments,examples of which are illustrated in the accompanying drawings. Whereverconvenient, the same reference numbers will be used throughout thedrawings to refer to the same or like parts.

The term “transaction card,” as used herein, may refer to a physicalcard product that includes features to provide transaction information.As used herein, the term “visible information” may include “personalinformation,” that is, information which is associated with a customerof the card or information associated with an account of/for the cardcustomer. In some embodiments, visible information may include“transaction information,” such as financial information (e.g., cardnumbers, account numbers, expiration dates, etc.), quasi-financialinformation (e.g., rewards program identification, discount information,etc.), individual-identifying information (e.g., name, address,signature, etc.), bank information, and/or transaction networkinformation. In some embodiments, visible information may serve as asecurity element (e.g., to prevent fraud) for the transaction cards,such as signatures or signature specimens, card numbers, expirationdates, or the like. Examples of transaction cards include credit cards,debit cards, gift cards, rewards cards, frequent flyer cards,merchant-specific cards, discount cards, identification cards,membership cards, and driver's licenses, but are not limited thereto.The physical properties of the transaction card (e.g., size,flexibility, location of various components included in the card) maymeet the various international standards, including, for example,ISO/IEC 7810, ISO/IEC 7811, ISO/IEC 7812, ISO/IEC 7813, ISO/IEC 7816,ISO 8583, ISO/IEC 4909, and ISO/IEC 14443. For example, a transactioncard may have a dimension of 85.60 mm (width) by 53.98 mm (height) by0.76 mm (thickness), as specified in ISO/ICE 7810.

FIGS. 1A-1C show front-, rear-, and edge-view illustrations,respectively, of an exemplary embodiment of transaction card 100. Thefront-view illustration of FIG. 1A shows a first side 102 (e.g., a frontside) of transaction card 100, and the rear-view illustration of FIG. 1Bshows a second side 104 (e.g., a rear side) of transaction card 100opposite the first side 102. That is, first side 102 may face a firstdirection outward from a center of transaction card 100, and second side104 may face a second direction outward from the center of transactioncard 100 such that the second direction is generally opposite the firstdirection. For example, transaction card 100 may have athree-dimensional structure with a first dimension D₁ (e.g., a width), asecond dimension D₂ (e.g., a length), and a third dimension D₃ (e.g., athickness), wherein the first side 102 and second side 104 of card 100are separated by at least one of D₁, D₂, and D₃. As shown in FIG. 1C,first and second sides 102 and 104 of transaction card 100 are separatedby D₃ (e.g., a thickness of card 20). It is noted that transaction card100 is not limited to rectangular shapes and designs, and thatdimensions D₁, D₂, and D₃ may vary with respect to one another such thattransaction card 100 may resemble a different shape.

As shown in FIG. 1A, first side 102 of transaction card 100 may includevisible information 110. Visible information 110 may include, forexample, personal information, such as information that is associatedwith a card, a customer of the card, or information relating to anaccount associated with the card or card customer. In some embodiments,visible information 110 may include visible information as defined aboveand/or other information. As will be explained below, visibleinformation 110 may be disposed on a surface of transaction card 100 toenable information to be visible from first side 102 of transaction card100. In other embodiments, visible information 110 may also oralternatively be disposed on a surface of transaction card 100 to enableinformation to be visible from another side of transaction card 100,such as second side 104.

Data storage component 112 may also be visible, exposed, or otherwiseaccessible (e.g., visibly, mechanically, or electronically) from firstside 102 of transaction card 100. For example, data storage component112 (e.g., an EMV chip) may be accessible through an aperture 114 (shownin FIG. 1A), recess, or other type of opening on first side 102 oftransaction card 100. In some embodiments, data storage component 112and aperture 114 may be located on a different side of transaction card100, such as second side 104. In other embodiments, first side 102 oftransaction card 100 may not include data storage component 112 oraperture 114. As used herein, a “data storage component” may be one ormore devices and/or elements configured to receive, store, process,provide, transfer, send, delete, and/or generate information. Forexample, data storage component 112 may be a microchip (e.g., a Europay,MasterCard, and Visa (EMV) chip), a communication device (e.g., NearField Communication (NFC) antenna, Bluetooth® device, WiFi device), amagnetic stripe, a barcode, Quick Response (OR) code, etc. Data storagecomponent 112 may be secured, affixed, attached, or the like, toaperture 114 in such a way that allows aperture 144 to carry datastorage component 112 while maintaining a utility of data storagecomponent 112 (i.e., allowing data storage component 112 to interactwith a point-of-sales (POS) terminal). Data storage component 112 may beconfigured to ensure that data storage component 112 functions propertyduring data storage and transmission, for example, ensuring that a cardcontaining a RFID (radio frequency identification) device shielded by amaterial layer can still be property read by a RFID reader through thematerial layer.

As shown in FIG. 1B, visible information 120 may be disposed on and/orvisible from second side 104 of transaction card 100. Visibleinformation 120 may include the same or different information withrespect to visible information 110 (referring to FIG. 1A). For example,visible information 120 may include visible information as describedabove as well as contact information, a serial number, a hologram,manufacturer information, and/or other information.

A data storage component 122 (e.g., a magnetic stripe) may be visiblefrom, disposed on, or otherwise accessible (e.g., visibly, mechanically,or electronically) from second side 104 of transaction card 100.Although data storage component 122 is shown in FIG. 1B as extendingalong dimension D₂ (e.g., a length of transaction card 100), it isunderstood that data storage component 122 may extend along a differentdimension (e.g., D₁) or multiple dimensions. In some embodiments, secondside 104 of transaction card 100 may not include data storage component122. In other embodiments, data storage component 122 may be included onfirst side 102 of transaction card 100.

FIG. 2 is a schematic diagram illustrating an exemplary systemenvironment to enable the sourcing of visible information using ascalable vector format, consistent with disclosed embodiments. FIG. 2shows a diagram of an exemplary system 200, consistent with disclosedembodiments, revealing some technical aspects of the present disclosurefor achieving the intended results of the present disclosure. Referringto FIG. 2 , system 200 may include customer terminal(s) 202, visibleinformation engine 204, network 206, intermediary service(s) 208,database(s) 210, server cluster(s) 212, cloud server(s) 214, lasermachine 216, and transaction card 100. The components and arrangement ofthe components included in system 200 may vary. Thus, system 200 mayfurther include other components or devices that perform or assist inthe performance of one or more processes consistent with the disclosedembodiments. The components and arrangements shown in FIG. 2 are notintended to limit the disclosed embodiments, as the components used toimplement the disclosed processes and features may vary.

As shown in FIG. 2 , a plurality of customer terminals 202 may beimplemented using a variety of different equipment, such assupercomputers, personal computers, servers, mainframes, mobile devices,smartphones, tablets, etc. In some embodiments, customer terminals 202may be associated with a financial service provider. In someembodiments, customer terminals 202 may belong to a customer. Customerterminals 202, in some embodiments, may be a machine or kiosk such as anautomated teller machine (ATM), etc. In some embodiments, customerterminals 202 may be configured to receive input from a customer, suchas input (e.g., visible information) regarding a transaction card.

Visible information engine 204 may be implemented using differentequipment, such as one or more supercomputers, one or more personalcomputers, one or more servers (e.g., server clusters 212 and/or cloudservice 214), one or more mainframes, one or more mobile devices, or thelike. In some embodiments, visible information engine 204 may comprisehardware, software, and/or firmware modules. Visible information engine204 may be configured to enable the sourcing of visible informationusing a scalable vector format. For example, visible information engine204 may source visible images by providing instructions that will allowa customer of a financial service provider to capture, map, resize,convert, and/or save an image. Visible information engine 204 may alsobe configured to verify visible information entered into apoint-of-service terminal with a scalable vector formatted filerepresenting the visible information stored for a transaction card.

Visible information engine 204, in some embodiments, may be storedlocally on customer terminals 202. In some embodiments, visibleinformation engine 204 may be stored remotely from customer terminals202. In some embodiments, visible information engine 204 may be storedon the one or more servers of the financial service provider (e.g., abank, credit union, credit card issuer, or other type of financialservice entity). In some embodiments, an employee representing afinancial service provider may input a plurality of visible information(e.g., a customer's signature). Furthermore, in some embodiments, anemployee representing the financial service provider may assist ininputting a plurality of visible information. In some embodiments,customer terminals 202 and/or visible information engine 204 may requirea customer to satisfy one or more security measures. For example, acustomer may be required to input or speak a password, social securitynumber, an account number, or the like. As another example, a customermay be required to enter biometric data such as a fingerprint or an eyescan. A customer may also be required to enter or select a pattern ofimages, spoken words, text, or the like. Even further, as an example, acustomer may be required to answer security questions or completevarious anti-hacking or cracking security measures such reCAPTCHA. Insome embodiments, after satisfying one or more security measures,visible information engine 204 may associate the customer with afinancial account and accept the financial transactions for thatfinancial account.

In some embodiments, visible information engine 204 may engage a cameraof customer terminals 202 to take a picture of visible information(e.g., a customer's signature) provided by the customer. As anotherexample, visible information engine 204 may cause customer terminals 202to execute a web browser that may allow a customer to input (i.e.,upload) a stored picture or file comprising visible information. In someembodiments, visible information engine 204 may cause customer terminals202 to send the inputted picture of visible information to visibleinformation engine 204 for processing.

Network 206, in some embodiments, may comprise one or moreinterconnected wired or wireless data networks that receive data fromone service or device (e.g., visible information engine 204) and send itto another service or device (e.g., intermediary services 208, databases210, server clusters 212, cloud service 214). For example, network 206may be implemented as one or more of the Internet, a wired Wide AreaNetwork (WAN), a wired Local Area Network (LAN), a wireless LAN (e.g.,IEEE 802.11, Bluetooth, etc.), a wireless WAN (e.g., WiMAX), and thelike. Each component in system 200 may communicate bidirectionally withother system 200 components either through computer network 206 orthrough one or more direct communication links, (not all are shown).

Intermediary services 208 may be implemented using different equipment,such as one or more supercomputers, one or more personal computers, oneor more servers (e.g., server clusters 212 and/or cloud service 214),one or more mainframes, one or more mobile devices, or the like. In someembodiments, intermediary services 208 may comprise hardware, software,and/or firmware modules.

In some embodiments, intermediary service 208 may contain instructionsto properly associate inputted data including visible informationreceived from visible information engine 204 with previously storedvisible information associated with a customer. In some embodiments,intermediary service 208 may store the associated input data includingvisible information into the database. In other embodiments,intermediary service 208 may send this inputted data including visibleinformation to laser machine 216 for processing. Intermediary service208, in some embodiments, may update customers associated with afinancial account regarding the updated visible information. Forexample, the plurality of intermediary services 208 could send customersan update using electronic messaging, such as text, email, or the like.In some embodiments, intermediary services 208 could cause a physicalmailing to be mailed to the customers. In some embodiments, intermediaryservices 208 could cause customer terminals 202 and/or visibleinformation engines 204 to update the customers. For example,intermediary services 208 could cause terminal 202 and/or visibleinformation engine 204 to display the updated information to thecustomers or send customers an update using electronic messaging, suchas text, email, or the like. Intermediary services 208 may also containinstruction to handle visible information associated with a customer.

Databases 210 may be configured to store information consistent with thedisclosed embodiments. In some aspects, components of system 200 (shownand not shown) may be configured to receive, obtain, gather, collect,generate, or produce information to store in databases 210. In certainembodiments, for instance, components of system 200 may receive orobtain information for storage over communications network 206. By wayof example, databases 210 may store information associated with aplurality of customers. The information may include personalinformation, transaction information, transaction network information,contact information, inputted data into visible information engine 204,and/or other information. In another example, databases 210 may storeresponses produced by and requests to visible information engine 204. Inother aspects, components of system 200 may store information indatabases 210 without using a computer network 206 (e.g., via a directconnection). In some embodiments, components of system 200, includingbut not limited to visible information engine 204, may use informationstored in databases 210 for processes consistent with the disclosedembodiments.

Server clusters 212 may be located in the same data center or differentphysical locations. Multiple server clusters 212 may be formed as a gridto share resources and workloads. Each server cluster 212 may include aplurality of linked nodes operating collaboratively to run variousapplications, software modules, analytical modules, rule engines, etc.Each node may be implemented using a variety of different equipment,such as a supercomputer, personal computer, a server, a mainframe, amobile device, or the like. In some embodiments, the number of serversand/or server clusters 212 may be expanded or reduced based on workload.In some embodiments, one or more components of visible informationengine 204 (including one or more server clusters 212) may be placedbehind a load balancer to support high availability and ensure real-time(or near real-time) processing of optimal decision predictions,consistent with disclosed embodiments.

Cloud service 214 may include a physical and/or virtual storage systemassociated with cloud storage for storing data and providing access todata via a public network such as the Internet. Cloud service 214 mayinclude cloud services such as those offered by, for example, Amazon®,Apple®, Cisco®, Citrix®, IBM®, Joyent®, Google®, Microsof®t, Rackspace®,Salesforce.com®, and Verizon®/Terremark®, or other types of cloudservices accessible via network 206. In some embodiments, cloud service214 comprises multiple computer systems spanning multiple locations andhaving multiple databases or multiple geographic locations associatedwith a single or multiple cloud storage services. As used herein, cloudservice 214 refers to physical and virtual infrastructure associatedwith a single cloud storage service. In some embodiments, cloud service214 manages and/or stores data associated with the disclosedembodiments.

Laser machine 216 may include a physical and/or virtual storage systemassociated with storage for storing data and providing access to datavia a public network such as the Internet. Laser machine 216 may also beconfigured to generate (e.g., using a laser to effect a property changeon something because of chemical or molecular alteration, burning,foaming, melting, charring, ablation, etching, printing, or the like)high-quality images processed by visible information engine 204 ontotransaction card 100 using vector formatted file types. In someembodiments, configuring laser machine 216 involves providing a firmwareupdate. For example, in some embodiments, a remote server may cause thisfirmware to update remotely. In other embodiments, a person may causethis firmware to update manually and/or locally. Vector formatted filetypes that may be compatible with laser machine 216 may include ScalableVector Graphics (SVG), Encapsulated PostScript (EPS), Drawing (DWG), orthe like. In some embodiments, these vector formatted file may becompatible with a controller of laser machine 216. In other embodiments,the vector formatted file may be compatible with a third-partyapplication (e.g., a CAM software application). Laser machine 216 alsomay be configured to create property changes resulting in visibleinformation (e.g., a customer's signature) being form on transactioncard 100, which can be made from various materials, such as metal, wood,fabric, plastic, copper, or the like. In some embodiments, laser machine216 may receive drive signals that instruct a carriage to move the layerand the laser to intensify output. In some embodiments, laser machine216 may use a continuous laser beam. In some embodiments, laser machine216 may use a pulsating laser beam.

FIG. 3 is a diagram of an exemplary visible information engineconfigured to perform functions of the disclosed methods, consistentwith disclosed embodiments. As shown, visible information engine 204 mayinclude one or more processor 360, input/output (“I/O”) devices 370, andmemory 380 storing data and programs 382 (including, for example,operating system 388). As noted above, visible information engine 204may be a single server or may be configured as a distributed computersystem including multiple servers or computers (e.g., server clusters212 and/or cloud service 214) that interoperate to perform one or moreof the processes and functionalities associated with the disclosedembodiments. In some embodiments, visible information engine 204 isspecially configured with hardware and/or software modules forperforming functions of disclosed methods. For example, visibleinformation engine 204 may include programs 382 (including operatingsystem 388) and/or visible information module(s) 392. The modules can beimplemented as specialized circuitry integrated within processor 360 orin communication with processor 360, and/or specialized software storedin memory 380 (as depicted in FIG. 3 ) executable by processor 360.

Processor 360 may be one or more known or custom processing devicesdesigned to perform functions of the disclosed methods, such as a singlecore or multiple core processors capable of executing parallel processessimultaneously. For example, processor 360 may be configured withvirtual processing technologies. In certain embodiments, processor 360may use logical processors to execute and control multiple processessimultaneously. Processor 360 may implement virtual machinetechnologies, including a Java® Virtual Mmachine, or other knowntechnologies to provide the ability to execute, control, run,manipulate, store, etc., multiple software processes, applications,programs, etc. In another embodiment, processor 360 may include amultiple-core processor arrangement (e.g., dual core, quad core, etc.)configured to provide parallel processing functionalities to allowvisible information engine 204 to execute multiple processessimultaneously. One of ordinary skill in the art would understand thatother types of processor arrangements could be implemented that providefor the capabilities disclosed herein.

Visible information engine 204 may also include one or more I/O devices370 that may comprise one or more interfaces for receiving signals orinput from devices and providing signals or output to one or moredevices that allow data to be received and/or transmitted by visibleinformation engine 204. Visible information engine 204 may also includeinterface components that display information and/or provide interfacesto one or more input devices, such as one or more keyboards, mousedevices, and the like, that enable in visible information engine 204 toreceive input from a customer or administrator (not shown).

Visible information engine 204 may include one or more storage devicesconfigured to store information used by processor 360 (or othercomponents) to perform certain functions related to the disclosedembodiments. In one example, visible information engine 204 may includememory 380 that includes instructions to enable processor 360 to executeone or more applications, such as server applications, networkcommunication processes, and any other type of application or softwareknown to be available on computer systems. Alternatively oradditionally, the instructions, application programs, etc., may bestored in an internal database or external storage (not shown) in directcommunication with visible information engine 204, such as one or moredatabase or memory accessible over network 206. The internal databaseand external storage may be a volatile or non-volatile, magnetic,semiconductor, tape, optical, removable, non-removable, or other type ofstorage device or tangible (i.e., non-transitory) computer-readablemedium.

Visible information engine 204 may also be communicatively connected toone or more remote memory devices (e.g., remote databases (not shown))through network 206 or a different network. The remote memory devicesmay be configured to store information (e.g., structured,semi-structured, and/or unstructured data) and may be accessed and/ormanaged by visible information engine 204. By way of example, the remotememory devices may be document management systems, Microsoft® SQLdatabase, SharePoint® databases, Oracle® databases, Sybase™ databases,or other relational databases. Systems and methods consistent withdisclosed embodiments, however, are not limited to separate databases oreven to the use of a database.

In one embodiment, visible information engine 204 may include memory 380that includes instructions that, when executed by processor 360, performone or more processes consistent with the functionalities disclosedherein. Methods, systems, and articles of manufacture consistent withdisclosed embodiments are not limited to separate programs or computersconfigured to perform dedicated tasks. For example, visible informationengine 204 may include memory 380 that may include one or more programs382 and/or visible information modules 392 to perform one or morefunctions of the disclosed embodiments. Moreover, processor 360 mayexecute one or more programs located remotely from system 200. Forexample, visible information engine 204 may access one or more remoteprograms, that, when executed, perform functions related to disclosedembodiments.

Memory 380 may include one or more memory devices that store data andinstructions used to perform one or more features of the disclosedembodiments. For example, memory 380 may represent a tangible andnon-transitory computer-readable medium having stored therein computerprograms, sets of instructions, code, or data to be executed byprocessor 360. Memory 380 may include, for example, a removable memorychip (e.g., EPROM, RAM, ROM, DRAM, EEPROM, flash memory devices, orother volatile or non-volatile memory devices) or other removablestorage units that allow instructions and data to be accessed byprocessor 360.

Memory 380 may also include any combination of one or more relationaland/or non-relational databases controlled by memory controller devices(e.g., server(s), etc.) or software, such as document managementsystems, Microsoft® SQL database, SharePoint® databases, Oracle®databases, Sybase™ databases, other relational databases, ornon-relational databases such as key-value stores or NoSQL™ databasessuch as Apache HBase™. In some embodiments, memory 380 may comprise anassociative array architecture, such as a key-value storage, for storingand rapidly retrieving large amounts of information.

Programs 382 stored in memory 380 and executed by processor(s) 360 mayinclude one or more operating system 388. Programs 382 may also includeone or more machine learning, trending, and/or pattern recognitionapplications (not shown) that cause processor(s) 360 to execute one ormore processes related to identifying, scoring, and/or ranking oftransaction structures. For example, the one or more machine learning,trending, and/or pattern recognition applications may provide, modify,or suggest input variables associated with one or more other programs382.

FIG. 4 is a flowchart of an exemplary process for electronicallyenabling the sourcing of visible information using a scalable vectorformat, consistent with disclosed embodiments.

At step 402, consistent with disclosed embodiments, visible informationmodules 392 may receive a request to add visible information (e.g., acustomer's signature) to a card. For example, in some embodiments,visible information modules 392 may receive this request because acustomer of a financial service provider would like to order a newtransaction card 100 or update an existing transaction card 100. Acustomer of a financial service provider may be an actual customer or aperspective customer of the financial service provider. As anotherexample, in other embodiments, visible information modules 392 mayreceive this request from the customer or financial service provider forother reasons.

In some embodiments, step 402 may comprise receiving a request to addvisible information after a customer or a financial service provider hasinitiated the process to issue a new card or update a preexisting card.In some embodiments, a financial service provider may send the customera link (e.g., a hyperlink, OR code, telephone number, or the like) forthe issuance of a new card or to update a preexisting card. A customermay send the link via the financial service provider as a recommendationto another customer. In other embodiments, an online advertisement forthe financial service provider may include the link or the financialservice provider may send the link to a customer. In other embodiments,the financial service provider could send the link to a customer in aphysical mailing. In some embodiments, visible information modules 392may receive a request to add visible information after a customer hasfilled out forms containing other visible information, such as personalinformation, transaction information, transaction network information,contact information, a serial number, a hologram, manufacturerinformation, and/or other information. Additionally, in someembodiments, visible information modules 392 may use intermediaryservices 208 to determine whether a customer is approved based on thecustomer credit information, preexisting account information with thefinancial service provider, internal parameters set by the financialservice provider, the risk of fraud, or the like. This approval may be anew transaction card before receiving a request to add visibleinformation (e.g., a customer's signature) to order a new transactioncard 100 or update an existing transaction card 100. In someembodiments, visible information modules 392 may receive a request toadd visible information after a customer has been presented with aprompt to add visible information by visible information modules 392.

Consistent with disclosed embodiments, at step 404, visible informationmodules 392 may capture an image of visible information (e.g., acustomer's signature). In some embodiments, to capture an image mayinvolve capturing a representation of an image (e.g., apressure-sensitive imprint.) In some embodiments, capturing an image ofvisible information includes causing customer terminals 202 to enable aninput/output device, such as a camera or the like, to allow the customerto take a picture of the visible information. In some embodiments,visible information modules 392 may obtain verification from thecustomer before causing the camera of customer terminals 202 to beenabled. Obtaining verification may involve providing instructions tocause customer terminals 202 to display a prompt that allows a customerto choose between option(s) that indicate whether the customer intendsto allow visible information modules 392 to cause customer terminals 202to enable a camera of customer terminals 202. In other embodiments,visible information modules 392 may provide instructions to causecustomer terminals 202 to enable one or more of its cameras withoutverification. After a customer activates the one or more cameras andtakes a picture, visible information modules 392 may receive an imagefile representative of the picture. In other embodiments, capturingvisible information may include providing instructions to cause customerterminals 202 to display a prompt that allows a customer to upload apreexisting image stored in hardware on customer terminals 202.

Consistent with disclosed embodiments, at step 406, visible informationmodules 392 may allow a customer to map and resize an image of visibleinformation (e.g., a customer's signature). In some embodiments, visibleinformation modules 392 may provide instructions to cause customerterminals 202 to display a bounding box. A bounding box, in someembodiments, comprises an enclosed area that designed for contents tofit inside of it. In some embodiments, a bounding box has a border thatis visually distinct from the area inside of the border. A bounding boxmay be any shape, size, or color. The bounding box may be configured tobe any size and in any position on transaction card 100. For example,the bounding box may be displayed on customer terminals 202 over orunderneath the first side 102 or the second side 104 of transaction card100. As another example, in some embodiments, the size of the boundingbox may be dependent on the size of transaction card 100. As a furtherexample, in some embodiments, the position, size, shape, and othercharacteristics of the bounding box could vary based on the type,material, size, color, etc., of transaction card 100.

Additionally, the bounding box may be used as a guide by the customer toresize the received captured image manually. For example, visibleinformation modules 392 may provide instructions to cause customerterminals 202 to display a bounding box and an unaltered captured image.Visible information modules 392 may provide instructions to causecustomer terminals 202 to allow a customer to drag and resize the imageso that a customer could cause the image to fit inside of the boundingbox. In other embodiments, visible information modules 392 may provideinstructions to cause customer terminals 202 to display a bounding boxbefore the image is captured. For example, the bounding box may betransparent except for the border of the bounding box, so that acustomer could line-up visible information (e.g., a customer'ssignature) to be within the bounding box before the image is captured bya camera of customer terminals 202.

In some embodiments, visible information modules 392 may provideinstructions to cause customer terminals 202 to indicate that thevisible information is inside of the bounding box. For example, visibleinformation modules 392 may provide instructions to cause customerterminals 202 to change the color of the bounding box's border to redwhen part of the visible information (e.g., a customer's signature) isoutside of the bounding box and green when the visible information iscompletely inside of the bounding box. In some embodiments, when thevisible information is completely inside the bounding box, visibleinformation modules 392 may cause customer terminals 202 to display anotification indicating that the resize was a success and automaticallymove on to the next steps.

In some embodiments, a customer can cause customer terminals 202 to senda notification to visible information modules 392 that the customer isdone with mapping and resizing the image in the bounding box. Forexample, the customer may send a notification that the customer is doneby tapping the screen, selecting a button, speaking, gesturing, or thelike. In other embodiments, visible information modules 392 may map andresize the image to fit inside of the bounding box automatically byusing mathematical formulas/algorithms, such as interpolation, sampling,or transformations, to fit the image inside of the bounding box. In someof the embodiments, visible information modules 392 may cause customerterminals 202 to display this automatically mapped and resized image inthe bounding box.

At step 408, consistent with disclosed embodiments, visible informationmodules 392 may convert the resized image into vector formats, such asSVG, EPS, DWG, or the like. In some embodiments, visible informationmodel 392 may convert the resized image from a flat image format (e.g.,PNG) to vector form. For example, visible information model 392 may usean outside process, known as an image tracer, vectorization program, orthe like, that takes the resized image saved in a flat image format andconverts it to a vector image. In other embodiments, visible informationmodel 392 may convert the resized image saved in a flat image format toa vector image on its own using various mathematical formulas anddigital processing techniques. In other embodiments, step 408 may not beneeded when customer terminals 202 may have saved the image as a vectorformat on image capture (e.g., during one of steps 404 and 406).

At step 410, consistent with disclosed embodiments, visible informationmodules 392 may save an image of the visible information. In someembodiments, visible information modules 392 may save a converted imageof the visible information to database 210. Saving the converted imageto the database may comprise associating the saved image of visibleinformation with other visible information, such as transactioninformation, personal information, or the like. In some embodiments,visible information modules 392 may communicate with intermediaryservices 208 to associate and save the image of visible information to adatabase. In some embodiments, visible information modules 392 maycommunicate with intermediary services 208 to save the image of visibleinformation on transaction card 100 during the manufacturing process.For example, once a transaction card has been created by laser machine216, visible information modules 392 may cause intermediary services 208to save the image of visible information on data storage component 112and/or data storage component 122 of transaction card 100. In someembodiments, visible information modules 392 may cause intermediaryservices 208 to save the image of visible information on server clusters212 and/or cloud service 214. In some embodiments, visible informationmodules 392 may save the image of visible information on transactioncard 100, server clusters 212, and/or cloud service 214.

At step 412, consistent with disclosed embodiments, visible informationmodules 392 may provide the image of visible information (e.g., acustomer's signature) to laser machine 216. In some embodiments,providing the image of visible information to laser machine 216 mayinclude causing laser machine 216 to laser onto transaction card 100 theimage of visible information. In some embodiments, laser machine 216will create visible information 110 or 120 by laser positioning andintensity commands based on the components of the vector formatted imageof visible information. In some embodiments, visible information modules392 may receive a response from laser machine 216 indicating that theimage of visible information is of an incompatible file type. Inresponse to receiving an error for incompatible file type, in someembodiments, visible information modules 392 may convert and resave theimage of visible information into a compatible vector file type.

FIG. 5 is a schematic diagram illustrating an exemplary transactionsystem, consistent with disclosed embodiments. Transaction system 500may include a computing system configured to receive and sendinformation between the components of transaction system 500 andcomponents outside of transaction system 500. Transaction system 500 mayinclude a financial service provider system 512 and a merchant system514 that may comprise POS terminal(s) 516, communicating with each otherthrough a network 518. Transaction system 500 may include additionaland/or alternative components.

Financial service provider system 512 may include one or more computersystems associated with an entity that provides financial services. Forexample, the entity may be a bank, credit union, credit card issuer, orother type of financial service entity that generates, provides,manages, and/or maintains financial service accounts for one or morecustomers. Financial service accounts may include, for example, creditcard accounts, checking accounts, savings accounts, loan accounts,reward accounts, and other types of financial service accounts.Financial service accounts may be associated with physical transactioncards 100, such as credit or debit cards that customers use to performfinancial service transactions, such as purchasing goods and/or servicesonline or at a terminal (e.g., POS terminal, mobile device, computer,etc.). Financial service accounts may also be associated with electronicfinancial products and services, such as a digital wallet or similaraccount that may be used to perform electronic transactions, such aspurchasing goods and/or services online.

Financial service provider system 512 may be implemented using differentequipment, such as one or more supercomputers, one or more personalcomputers, one or more servers (e.g., server clusters 212 and/or cloudservice 214), one or more mainframes, one or more mobile devices, or thelike. In some embodiments, financial service provider 512 may comprisehardware, software, and/or firmware modules. In some embodiments,financial service provider 512 may store on its one or more serverssystem 200 and/or visible information engine 204. Financial serviceprovider 512 may also be comprised of a plurality of programs stored onmemory and one or more processors, or the like.

Merchant system 514 may include one or more computer systems associatedwith a merchant. For example, merchant system 514 may be associated withan entity that provides goods and/or services (e.g., a retail store).The merchant may include brick-and-mortar location(s) that a customermay physically visit and purchase goods and services using thetransaction cards. Such physical locations may include computing devices(e.g., merchant system 514) that perform financial service transactionswith customers (e.g., POS terminals 516). Additionally or alternatively,merchant system 514 may be associated with a merchant who provides anelectronic shopping environment, such as a website or other onlineplatform that consumers may access using a computer through a browser, amobile application, or similar software. Merchant system 514 may includea client device, such as a laptop computer, desktop computer,smartphone, or tablet, which a customer may operate to access theelectronic shopping mechanism. Merchant system 514 may be implementedusing different equipment, such as one or more supercomputers, one ormore personal computers, one or more servers (e.g., server clusters 212and/or cloud service 214), one or more mainframes, one or more mobiledevices, or the like. Merchant system 514 may also be comprised of aplurality of programs stored on memory and one or more processors, orthe like.

POS terminals 516 may be implemented using different equipment, such asone or more supercomputers, one or more personal computers, one or moreservers (e.g., server clusters 212 and/or cloud service 214), one ormore mainframes, one or more mobile devices, or the like. POS terminals516 may also be comprised of a plurality of programs stored on memoryand one or more processors, or the like.

Network 518 may include any type of network configured to facilitatecommunications and data exchange between components of transactionsystem 500, such as, for example, financial service provider system 512and merchant system 514. Network 518 may include, but is not limited to,Local Area Networks (LANs) and Wide Area Networks (WANs), such as theInternet. Network 518 may be a single network or a combination ofnetworks. Network 518 is not limited to the above examples andtransaction system 500 may implement any type of network that allowsentities (shown and not shown) of transaction system 500 to exchangedata and information.

Transaction system 500 may be configured to conduct a transaction usingtransaction card 100. In some embodiments, financial service providersystem 512 may provide transaction card 100 to a customer for use inconducting transactions associated with a financial service account heldby the customer. For example, the customer may use transaction card 100at a merchant location to make a purchase. During the purchase,information may be transferred from transaction card 100 to merchantsystem 514 (e.g., POS 516). Merchant system 514 may communicate withfinancial service provider system 512 via network 518 to verify theinformation and to complete or deny the transaction. For example,merchant system 514 may receive account information from transactioncard 100. Merchant system 514 may transmit the account information and apurchase amount, among other transaction information, to financialservice provider system 512. Financial service provider system 512 maysettle the transaction by transferring funds from the customer'sfinancial service account to a financial service account associated withthe merchant.

While transaction system 500 and transaction card 100 are depicted anddescribed in relation to transactions that involve customers, merchants,and financial service providers, it should be understood that theseentities are used only as an example to illustrate one environment inwhich transaction card 100 may be used. Transaction card 100 is notlimited to financial products and may be any physical card product thatis configured to store and/or transmit information. For example,transaction card 100 may be an identification card configured to provideinformation to a device in order to identify the holder of the card(e.g., a driver's license).

FIG. 6 is a flowchart of an exemplary process for electronicallyverifying visible information (e.g., a customer signature) entered intoa POS terminal with a scalable vector formatted file representingvisible information stored for a transaction card, consistent withdisclosed embodiments. In some embodiments, financial service providersystem 512 has one or more processors configured to store instructionsconsistent with the disclosed embodiments of visible information engine204 and/or system 200. In some embodiments, financial service providersystem 512 may utilize visible information engine 204 and/or system 200to process visible information.

At step 602, consistent with disclosed embodiments, financial serviceprovider system 512 may process a transaction for a customer usingtransaction card 100. A customer may attempt to pay for an item atmerchant system 514 by inserting transaction card 100 into POS terminals516. For example, a client may insert data storage component 112 (i.e.,an EMV chip) into POS terminals 516. As another example, a client mayswipe data storage component 122 (e.g., magnetic stripe) through amagnetic stripe reader on POS terminal 516. In some embodiments, thestored contents of either data storage component 112 and/or data storagecomponents 122 will be read by the POS terminal 516. In someembodiments, the stored contents of either component 112 and/or datastorage components 122 will include a vector image file of visibleinformation (e.g., a customer signature) and other visible information,such as one or more of personal information, transaction information,contact information, or the like.

At step 604, consistent with disclosed embodiments, POS terminal 516 mayrequest a customer to input visible information. In other embodiments,POS terminal 516 may require a customer to input visible information. Insome embodiments, a customer may input visible information by writingit. In some embodiments, visible information engine 204 of financialservice provider 512 may provide instructions to cause POS terminal 516to request or require a customer to input visible information. In otherembodiments, a customer may input visible information by typing it.

POS terminal 516 may provide a display containing a bounding box forvisible information to be digitally written on the screen of POSterminal 516. In some embodiments, visible information engine 204 offinancial service provider 512 may provide instructions to cause POSterminal 516 to provide a display containing a bounding box for visibleinformation to be digitally written on the screen of POS terminal 516.

Consistent with disclosed embodiments, at step 606, POS terminal 516 mayreceive input visible information (e.g., a customer's signature). Insome embodiments, POS terminal 516 may confirm that the customeracknowledges that the input visible information is accurate beforeaccepting the input visible information. In some embodiments, visibleinformation engine 204 of financial service provider 512 may provideinstructions to cause POS terminal 516 to confirm that the customeracknowledges that the input visible information is accurate beforeaccepting the input visible information. This confirmation can be done,for example, by requesting and receiving a notification from thecustomer acknowledging that the input visible information is accuratebefore accepting the input visible information.

At step 608, consistent with disclosed embodiments, POS terminal 516 maysend data representing the input visible information and a stored imageof visible information read from data storage component 112 and/or datastorage components 122 to visible information engine 204 of financialservice provider system 512 to determine the customer's inputted visibleinformation is valid. In some embodiments, visible information engine204 of financial service provider 512 may cause POS 516 to send thisdata. In some embodiments, financial service provider system 512 willcompare the data representing the input visible information with thestored image of visible information read from data storage component 112and/or data storage components 122. In other embodiments, financialservice provider system 512 will compare the data representing the inputvisible information with a vector formatted image of visible informationon its servers, saved consistently with step 410. In some otherembodiments, financial service provider system 512 will compare thestored vector formatted visible information read from data storagecomponent 112 and/or data storage components 122 with a saved vectorformatted image of visible information on its servers consistent withstep 410. To compare, for example, financial service provider system 512may run a similarity analysis using various mathematical principles ofvector formatting comparisons along with the vector formatting filecontents to determine a similarity score regarding the comparison.Financial service provider system 512 may then compare the similarityscore with a predetermined threshold to determine if the visibleinformation is valid.

Consistent with disclosed embodiments, if the input visible information(e.g., a customer's signature) is determined to be not valid, in someembodiments financial service provider system 512 may cause POS terminal516 to report that the payment is being rejected. Financial serviceprovider system 512 may instruct POS service to repeat steps 604 to 608in order to test if the determined visible information is valid aplurality of times. Financial service provider system 512 may have athreshold value of how many times the test can be completed before thetransaction is stopped. In some embodiments, financial service providersystem 512 may put a temporary hold on transaction card 100, preventingthe customer from completing any transactions with transaction card 100until the issue is resolved. Further, in some embodiments, financialservice provider 512 may require additional authentication to accept thetransaction, such as a secret code. In some embodiments, financialservice provider system 512 may report that a potential fraud hasoccurred and suspend transaction card 100. In some embodiments,financial service provider system 512 may notify authorities that afraud has occurred.

At step 612, consistent with disclosed embodiments, if the input visibleinformation is determined to be valid, in some embodiments, financialservice provider system 512 may cause POS terminal 516 to report thatthe payment is being accepted. Financial service provider system 512 maythen take funds from the transaction from the financial accountassociated with transaction card 100 and deliver them to the financialaccount of merchant system 514.

Descriptions of the disclosed embodiments are not exhaustive and are notlimited to the precise forms or embodiments disclosed. Modifications andadaptations of the embodiments will be apparent from consideration ofthe specification and practice of the disclosed embodiments. Forexample, the described implementations include hardware, firmware, andsoftware, but systems and techniques consistent with the presentdisclosure may be implemented as hardware alone. Additionally, thedisclosed embodiments are not limited to the examples discussed herein.

Computer programs based on the written description and methods of thisspecification are within the skill of a software developer. The variousprograms or program modules may be created using a variety ofprogramming techniques. For example, program sections or program modulesmay be designed in or by means of Java, C, C++, assembly language, orany such programming languages. One or more of such software sections ormodules may be integrated into a computer system, non-transitorycomputer-readable media, or existing communications software.

Moreover, while illustrative embodiments have been described herein, thescope includes any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations or alterations based on the presentdisclosure. The elements in the claims are to be interpreted broadlybased on the language employed in the claims and not limited to examplesdescribed in the present specification or during the prosecution of theapplication, which examples are to be construed as non-exclusive.Further, the steps of the disclosed methods may be modified in anymanner, including by reordering steps or inserting or deleting steps. Itis intended, therefore, that the specification and examples beconsidered as exemplary only, with the true scope and spirit beingindicated by the following claims and their full scope of equivalents.

What is claimed is:
 1. A computer-implemented method for sourcingvisible information, comprising: receiving, from a user device via acommunication network, in response to a first user input at the userdevice, and after a user has been presented with a prompt to add visibleinformation, a request to store information associated with a signatureon a transaction card, the user device comprising at least one of apoint of sale terminal, an automated teller machine (ATM), or a mobiledevice; receiving an image of the signature from the user device,wherein the image was captured by the user device in response to asecond user input at the user device; and saving, in response to thereceived request to store information associated with the signature onthe transaction card, image data based on the received image of thesignature to the transaction card.
 2. The computer-implemented method ofclaim 1, wherein the image data is saved to a data storage component ofthe transaction card.
 3. The computer-implemented method of claim 1,wherein the image data is saved to a data storage component of thetransaction card, the data storage component being a magnetic stripe oran EMV chip.
 4. The computer-implemented method of claim 1, wherein theimage was captured by a camera of the user device.
 5. Thecomputer-implemented method of claim 1, wherein the image of thesignature is received via a web browser.
 6. The computer-implementedmethod of claim 1, wherein the image of the signature is based on apressure-sensitive input.
 7. The computer-implemented method of claim 1,wherein the image data is vector format data.
 8. Thecomputer-implemented method of claim 7, further comprising convertingthe image of the signature into the vector format data.
 9. Thecomputer-implemented method of claim 1, wherein the image of thesignature is received as vector format data.
 10. Thecomputer-implemented method of claim 1, wherein: the image was capturedby at least one camera; and the at least one camera was enabled inresponse to the user device receiving verification information from auser.
 11. The computer-implemented method of claim 1, wherein the imagewas captured by the user device after the user device displayed abounding box.
 12. The computer-implemented method of claim 11, whereinat least one visual characteristic of the bounding box is based on atleast one of a type, material, size, or color of the transaction card.13. The computer-implemented method of claim 1, further comprisingassociating the image data with at least one of transaction informationor personal information associated with a user associated with therequest.
 14. The computer-implemented method of claim 13, wherein theassociated image data is vector format data.
 15. Thecomputer-implemented method of claim 1, further comprising convertingthe image data to a file type compatible with a laser machine.
 16. Thecomputer-implemented method of claim 1, wherein the transaction card isconfigured to provide the saved image data to a point-of-sale (POS)terminal for signature verification.
 17. The computer-implemented methodof claim 1, wherein a notification is provided at the user device inresponse to the signature fitting within a bounding box.
 18. Thecomputer-implemented method of claim 1, wherein the image was capturedby the user device further in response to the signature fitting within abounding box.
 19. The computer-implemented method of claim 1, wherein,prior to receiving the image of the signature, the image of thesignature was resized by the user device.
 20. A system for sourcingvisible information, comprising: one or more memory devices for storinginstructions; and one or more processors executing the instructions toperform operations comprising: receiving, from a mobile device via acommunication network in response to a first user input at the mobiledevice, and after a user has been presented with a prompt to add visibleinformation, a request to store information associated with a signatureon a transaction card; receiving an image of the signature from themobile device, wherein: the image was captured by the mobile device inresponse to a second user input at the mobile device; and capturing theimage involves capturing a pressure-sensitive input at the mobile deviceor capturing the image using a camera of the mobile device; and saving,in response to the received request to store information associated withthe signature on the transaction card, image data based on the receivedimage of the signature to the transaction card.